fix: remove scope qualifier from Maven/Gradle provider purls#388
Conversation
|
Isn't it expected as result of https://redhat.atlassian.net/browse/TC-2752 ? |
|
/review |
PR Reviewer Guide 🔍Here are some key observations to aid the review process:
|
The linked Jira refers to adding This PR removes the That is not done in any other package manager and in the Javascript client |
|
LGTM, but need a rebase. |
Purls no longer contain ?scope=compile or ?scope=provided qualifiers, aligning with the JS client. Test-scope filtering now uses DependencyAggregator.isTestDependency() instead of reading from purl qualifiers. CycloneDX component scope is still set via addDependency(). Implements TC-3920 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This method became dead code after the TC-3920 refactor that moved test-scope filtering to use DependencyAggregator.isTestDependency() directly in parseDependencyTree(). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Summary
?scope=compileand?scope=providedqualifiers from generated purls in Maven and Gradle providers, aligning with the JS clientDependencyAggregator.isTestDependency()instead of reading from purl qualifiersImplements TC-3920
Test plan
mvn verifypasses🤖 Generated with Claude Code